Monitoring Dynamics 365
Unlock proactive monitoring and management for Microsoft Dynamics 365! Nodinite empowers you to detect, resolve, and prevent issues—while optimizing license usage and reducing risk.
This section explains what Nodinite monitors in Dynamics 365 and how it translates data into actionable monitoring states. You can use a wide range of remote commands (Actions) to swiftly resolve issues—see [Managing Dynamics 365][Mana] for more details.
The agent auto-discovers all your deployed Dynamics 365 artifacts. Simply deploy new workflows or artifacts, and Nodinite will automatically detect, monitor, and list them in your Monitor Views.
Most monitoring options—including thresholds—are managed in the global Configuration.
Monitoring Features
- State Evaluation – Ensures Dynamics 365 and all deployed artifacts (Workflows, Processing steps) maintain the intended run-time state.
If Nodinite can't check the state of your Dynamics 365 workflows, chances are no one else can use them either.
- Auditing – Gain insights into user licensing and audit login activity.
- History – View execution history for all monitored artifacts.
- Automatic Discovery – Nodinite agents leverage Microsoft SDKs to automatically discover and monitor your Dynamics 365 environment. Sharing or restricting access to any workflow is easy and secure.
Overview of a Dynamics 365 group with examples of state evaluations.
Each artifact (e.g., a Workflow) appears in Nodinite as a unique Resource. If you have 42 Workflows, you'll see 42 Resources in Nodinite.
- [Resource][] names come from the deployed artifact in Dynamics 365.
- Application names are based on the Dynamics 365 Application.
- All artifacts of a given type belong to a Category.
Nodinite groups monitoring capabilities for the Dynamics 365 agent as Resources by Categories. Each [Monitoring Agent][Monitoring Agents] has unique Categories.
Nodinite Dynamics 365 Monitoring Agent also supports Remote Actions on most resources via the Web Client or programmatically through the Web API.
The following Categories are provided by the Nodinite Dynamics 365 Monitoring Agent:
Example list of Categories as filtered within a Monitor View.
Tip
Fine-tune user access with Roles and Monitor Views—grant access to everything, selected applications, categories, or even individual artifacts.
State evaluation for Dynamics 365
Depending on settings in the global Configuration there are many different options for the evaluation process.
Category | What is evaluated | Actions | Metrics/Statistics | |
---|---|---|---|---|
ActionBusiness Process FlowBusiness RuleProcessing stepWorkflow | Execution time | History | - | |
Resources in use | Resources in use | Details | - | |
User Logon Auditing | User Logon Auditing | List last 7 days List last logon date | - |
Execution time
The maximum allowed run-time for monitored categories are evaluated according to the settings in the global Configuration where the main ones are imaged below:
Application Name=Instance configuration name from the global Configuration
Category Name="Action | Business Process Flow | Business Rule | Processing step | Workflow"
Resource Name="Name of artifact as deployed within Dynamics 365"
The evaluated state is provided in the table below:
State | Status | Description | Actions | |
---|---|---|---|---|
Unavailable | Resource not available | If the resource be evaluated either due to network or security-related problems | Review prerequisites | |
Error | Workflow failed | One or more executions are failing | History | |
Error | Workflow has not completed run within defined time of... | Executions are not completing within time defined by the error threshold | History | |
Warning | Workflow has not completed run within defined time of | Executions are not completing within time defined by the warning threshold | History | |
OK | No problems detected | Executions are not failing and runs on time | History |
You can view the History and manage the entries in the list for the executions of selected monitored category.
Resources in use
Click the 'Details' menu item to further manage 'Resources in use'. This topic is further detailed in the Resources in use management user guide.
Example when 'Resources in use' are above warning threshold
Application Name=Instance configuration name from the global Configuration
Category Name="Audit"
Resource Name="User Access"
The evaluated state is provided in the table below:
State | Status | Description | Actions | |
---|---|---|---|---|
Unavailable | Resource not available | If the resource be evaluated either due to network or security-related problems | Review prerequisites | |
Error | Too many active users defined | Users have not logged on above configured threshold | Details | |
Warning | Too many active users defined | Number of users above configured error threshold | Details | |
OK | Operative users | Users are frequently logging on | Details |
User Logon Auditing
If you checked the 'Enable monitoring of inactive users' option in the Configuration and you have users who have not logged in to your Microsoft Dynamics 365 instance within user-defined thresholds the Resource 'User access' will be evaluated accordingly.
Application Name=Instance configuration name from the global Configuration
Category Name="Audit"
Resource Name="User Access"
The evaluated state is provided in the table below:
State | Status | Description | Actions | |
---|---|---|---|---|
Unavailable | Resource not available | If the resource be evaluated either due to network or security-related problems | Review prerequisites | |
Error | Inactive users found | Users have not logged on above configured threshold | List last 7 days List last logon date | |
Warning | Inactive users found | Users have not logged on above configured warning threshold | List last 7 days List last logon date | |
OK | Operative users | Users are frequently logging on | List last 7 days List last logon date |
This topic is further detailed in the User Audits management user guide.
Alert history for Dynamics 365
During root cause analysis or other purposes, it might be helpful to understand how often your Dynamics 365 instance(s) problems happen. If your Monitor View allows it, you can search for historical state changes for the provided time span, either for all monitored artifacts within Dynamics 365 or individually. This topic is further detailed within the generic instructions on how to Add or manage Monitor View page.
Search | Resource history |
---|---|
![]() |
![]() |
Frequently asked questions
Use the troubleshooting guide to find the FAQ and answers to known problems.
Next step
Managing Dynamics 365
Configuration